D3.2 Cost Concept Model and Gateway Specification

This document introduces a Framework supporting the implementation of a cost concept model against which current and future cost models for curating digital assets can be benchmarked. The value built into this cost concept model leverages the comprehensive engagement by the 4C project with various user communities and builds upon our understanding of the requirements, drivers, obstacles and objectives that various stakeholder groups have relating to digital curation. Ultimately, this concept model should provide a critical input to the development and refinement of cost models as well as helping to ensure that the curation and preservation solutions and services that will inevitably arise from the commercial sector as ‘supply’ respond to a much better understood ‘demand’ for cost-effective and relevant tools. To meet acknowledged gaps in current provision, a nested model of curation which addresses both costs and benefits is provided. The goal of this task was not to create a single, functionally implementable cost modelling application; but rather to design a model based on common concepts and to develop a generic gateway specification that can be used by future model developers, service and solution providers, and by researchers in follow-up research and development projects.<p></p> The Framework includes:<p></p> • A Cost Concept Model—which defines the core concepts that should be included in curation costs models;<p></p> • An Implementation Guide—for the cost concept model that provides guidance and proposes questions that should be considered when developing new cost models and refining existing cost models;<p></p> • A Gateway Specification Template—which provides standard metadata for each of the core cost concepts and is intended for use by future model developers, model users, and service and solution providers to promote interoperability;<p></p> • A Nested Model for Digital Curation—that visualises the core concepts, demonstrates how they interact and places them into context visually by linking them to A Cost and Benefit Model for Curation.<p></p> This Framework provides guidance for data collection and associated calculations in an operational context but will also provide a critical foundation for more strategic thinking around curation such as the Economic Sustainability Reference Model (ESRM).<p></p> Where appropriate, definitions of terms are provided, recommendations are made, and examples from existing models are used to illustrate the principles of the framework

GAP report between E-ARK requirements for access, and current access solutions

This report is a GAP analysis between current access services and user requirements for Access. It describes the landscape of access services today and highlights the results of the examinations of user needs for access services. The study targets the producers of the access services (service providers and archives), the clients of these services (archives) and the end-.‐users of them (third-.‐party users, the archives and the content providers themselves). This GAP analysis report can be read by readers uninvolved with the E-ARK project to gain understanding of the current situation and assess their own solution(s)

E‐ARK Dissemination Information Package (DIP) Final Specification

The primary aim of this report is to present the final version of the E-ARK Dissemination Information Package (DIP) formats. The secondary aim is to describe the access scenarios in which these DIP formats will be rendered for use

Records export, transfer and ingest recommendations and SIP Creation Tools

This report describes a software deliverable as it delivers a number of E-ARK tools: • ERMS Export Module (a tool for exporting records and their metadata from ERMS in a controlled manner); • Database Preservation Toolkit (a tool for exporting relational databases as SIARD 2.0 or other formats); • ESSArch Tools for Producer (a tool for SIP creation); • ESSArch Tools for Archive (a tool for SIP ingestion); • RODA-in (a tool for SIP creation); • Universal Archiving Module (a tool for SIP creation). In addition, an overview of Pre-Ingest and Ingest processes will be provided by this report which will help to understand the tools and their use

SMURF (Semantically Marked Up Record Format) Profile

The purpose of this report is to describe SMURF (semantically marked up record format) profile, which includes ERMS (electronic records management systems) and SFSB (simple file-system based) records as described below. When extracting information from a producer’s system one has the choice of two generic options: 1. Extracting data in a relational database structure Extracting data from a relational database into a long-term preservation format (SIARD) that preserves the properties of the relational database so that the data can be imported into a relational database management system (RDBMS) on Access. Access can happen via database queries or via a search field. The main access use cases are: a. The producer wishes to retrieve their data for business purposes and/or re-use. b. The consumer wishes to consult the data for purposes of research. c. The archivist wishes to retrieve the data for professional treatment: to check and, if necessary perform preservation actions, etc. More information about this option can be read in the SIARD 2.0 Profile Specification. 2. Extracting data and metadata as records Extract the records and normalise them to a standard E-ARK XML format. This means that the records are semantically marked up using metadata. Being technically valid and complying with this specification makes them directly accessible for validation, data management, indexing and searching. Their structured semantic metadata description is explicit rather than hidden inside a RDBS. The representation of descriptive metadata inside the archive can be in the E-ARK SMURF AIP format and/or another native archive format. The main advantages over the RDBS representation are that: o Records from different sources can be merged. o Search and access is possible across all records from all sources. o Records can be managed and accessed uniformly. o The original database / records system software does not need to be licensed and preserved

E‐ARK Search, Access and Display Interfaces

The aim of this report is to describe the “Search, Access and Display Interfaces” that have been developed in the Access component of the E-ARK project. The deliverable associated with this report is mainly a software deliverable and therefore this document provides only underpinning descriptions of and links to the software itself. The tools that are described and provided allow Consumers (ie. end-users and archivists) to: 1. Search and order records (primarily end-users, but also archivists) 2. Manage orders of records and manage the records themselves, including the AIP to DIP conversion (archivists only) 3. Access ordered records as DIPs (primarily end-users, but also archivists) In addition to the the introductory remarks in chapter 2, the functionality of the tools that allow the Consumers to search, manage, and access records is described in chapter 3. After the description of each tool, links are provided to code and documentation

Detailed Pilots Specification

The Electronic Archiving Service consists of a series of activities covered by software tools and manual workflow steps. These tools are currently partly in existence, some are being developed by E-ARK project, many more are to be added by developments of the digital preservation community in the future. The role of this report is to identify the most relevant scenarios for the E-ARK Service, define which scenario which level of activity is needed in order to bridge the gap of the currently existing solutions (e.g. integration, software development, interface definition

Documentation, Common Information and Short Overview of the E-ARK pilots

This report contains the common information and short overview of the pilots, along with references to the final version of the Pilot Definition Excel files and Pilot Documentation Packages

Best Practice:SIP specification, records export requirements, transfer and ingest

This report provides an overview of the current situation of the digital archiving best practices. Special attention is placed on archival ingest workflows, submission information package formats used for transfer and ingest of digital objects and their metadata. Records export best practices are covered as well. The report consists of the following parts: • introduction; • description of the methods used for the analysis; • overview of the results with short descriptions of practices, standards and tools; • recommendations for the E-ARK project; • appendices (the survey questions, an assessment of the interviewed stakeholders, the questions from the qualitative interview and a terminology list). The study concentrates on the following topics from the archival workflow: • Records export (Pre-Ingest workflow steps); • Steps in Ingest workflow; • Submission information packages (SIP) used. Highlighted points of this best practice report for E-ARK work are: • One high-level (pre-) ingest workflow is proposed in section 4 which consists of 4 phases of the PAIMAS methodology, but several existing workflow parts must be examined more deeply to include the common steps to the E-ARK archiving workflow; • E-ARK needs to develop detailed and commonly understood requirements for the records export process which include procedures for data selection, extraction, metadata mapping, validation and quality control as these are currently lacking; • One high-level SIP structure is proposed in section 4. (Recommendation for further work), but several existing SIP physical and logical structures must be examined more deeply to include the common aspects of formats used at archives into the E-ARK SIP specification